Skip to content

docs: tighten rustdoc crate and module headers - #603

Merged
mfw78 merged 1 commit into
dev/m1from
docs/598-rustdoc
Jul 25, 2026
Merged

docs: tighten rustdoc crate and module headers#603
mfw78 merged 1 commit into
dev/m1from
docs/598-rustdoc

Conversation

@mfw78

@mfw78 mfw78 commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

What

Doc-comment-only sweep of crate (lib.rs) and module headers across the workspace: trim discursive framing and stale version promises to the current contract, remove an external-project rationale citation, and purge em dashes from touched comments. No code, wit/, or Cargo metadata changed.

Highlights: nexum-sdk lib.rs (companionship + "why no generate!" essays cut), wit_bindgen_macro.rs ("before this macro existed" narrative cut), nexum-sdk-test (#94 planning ref and redb-fidelity dashes), the identity/messaging/remote-store host impls (now stated as unimplemented stubs), manifest mod.rs/types.rs and engine_config.rs (0.3 and M3/M4 scheduling removed), restart_policy.rs (0.3/M5 follow-up and tuneable promises removed), provider_pool.rs ("per alloy's own guidance" removed), and tools/load-gen (retargeted off the M4 label and the deleted e2e-prep.md reference).

Why

Part of the #598 cruft-sweep. Headers were describing planned states and rationale journeys rather than the shipped contract; the version-promise notes drift as milestones move.

Testing

RUSTDOCFLAGS="-D warnings" cargo doc --workspace --no-deps and cargo fmt --all --check, both via nix develop, pass. Diff verified comment-only.

AI Assistance

Documentation-only sweep; verified with the cargo doc and cargo fmt runs noted above.

Part of #598.

Trim discursive and stale rustdoc across the workspace: cut the wit-bindgen companionship and "why no generate!" essays in nexum-sdk to the factual contract, drop the "before this macro existed" narrative in wit_bindgen_macro, and remove the #94 planning reference in nexum-sdk-test.

Reduce version-promise notes to current behaviour: the identity, messaging, and remote-store host impls are stated as unimplemented stubs (confirmed against the code) rather than "deferred to 0.3"; manifest and engine-config headers drop the 0.3 and M3/M4 scheduling; restart_policy drops the 0.3/M5 follow-up and tuneable promises.

Remove the external-project rationale citation in provider_pool ("per alloy's own guidance"), retarget load-gen off the M4 label and the deleted e2e-prep.md reference, and purge em dashes from the touched doc comments.

Part of #598.
@mfw78
mfw78 merged commit e8a873e into dev/m1 Jul 25, 2026
7 checks passed
@mfw78
mfw78 deleted the docs/598-rustdoc branch July 25, 2026 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant